<div id="commit-files"></div>
<div class="header">
<p>
Next: [[cvs: Rcsinfo#Rcsinfo|rcsinfo]], Previous: [[cvs: The cvswrappers file#The cvswrappers file|Wrappers]], Up: [[cvs: Reference manual for Administrative files#Reference manual for Administrative files|Administrative files]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>

----

<div id="The-commit-support-files"></div>
=== The commit support files ===
<div id="index-Committing_002c-administrative-support-files"></div>

The &lsquo;<code>-i</code>&rsquo; flag in the &lsquo;<tt>modules</tt>&rsquo; file can be
used to run a certain program whenever files are
committed (see [[cvs: The modules file#The modules file|modules]]).  The files described in
this section provide other, more flexible, ways to run
programs whenever something is committed.

There are three kind of programs that can be run on
commit.  They are specified in files in the repository,
as described below.  The following table summarizes the
file names and the purpose of the corresponding
programs.

;&lsquo;<tt>commitinfo</tt>&rsquo;
: The program is responsible for checking that the commit is allowed.  If it exits with a non-zero exit status the commit will be aborted.

;&lsquo;<tt>verifymsg</tt>&rsquo;
: The specified program is used to evaluate the log message, and possibly verify that it contains all required fields.  This is most useful in combination with the &lsquo;<tt>rcsinfo</tt>&rsquo; file, which can hold a log message template (see [[cvs: Rcsinfo#Rcsinfo|rcsinfo]]).

;&lsquo;<tt>editinfo</tt>&rsquo;
: The specified program is used to edit the log message, and possibly verify that it contains all required fields.  This is most useful in combination with the &lsquo;<tt>rcsinfo</tt>&rsquo; file, which can hold a log message template (see [[cvs: Rcsinfo#Rcsinfo|rcsinfo]]).  (obsolete)

;&lsquo;<tt>loginfo</tt>&rsquo;
: The specified program is called when the commit is complete.  It receives the log message and some additional information and can store the log message in a file, or mail it to appropriate persons, or maybe post it to a local newsgroup, or&hellip;  Your imagination is the limit!

 [[cvs: The common syntax#The common syntax|&bull; syntax]]::                      The common syntax
 [[cvs: Commitinfo#Commitinfo|&bull; commitinfo]]::                  Pre-commit checking
 [[cvs: Verifying log messages#Verifying log messages|&bull; verifymsg]]::                   How are log messages evaluated?
 [[cvs: Editinfo#Editinfo|&bull; editinfo]]::                    Specifying how log messages are created
                                 (obsolete)
 [[cvs: Loginfo#Loginfo|&bull; loginfo]]::                     Where should log messages be sent?


----

<div class="header">
<p>
Next: [[cvs: Rcsinfo#Rcsinfo|rcsinfo]], Previous: [[cvs: The cvswrappers file#The cvswrappers file|Wrappers]], Up: [[cvs: Reference manual for Administrative files#Reference manual for Administrative files|Administrative files]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>
This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>].
